StrideAI iconStrideAI
Install free
v0.54Free extension for Azure DevOps

Your AI teammate, inside Azure DevOps.

Ask in plain language. StrideAI reads your work items, sprints, code, pull requests, and pipelines, and does the work with your approval.

Your own models · No StrideAI servers · No telemetry

dev.azure.com/contoso/Shop/_apps/hub/strideai.chatSimulated

How can I help today, Alex?

Ask anything, or work with items and code in Shop.

Search what StrideAI can do
{{ t.label }}
Quick start for
WorkbenchOne action on a whole sprint, a saved query, or a list of items
Message StrideAI · # work item, ! pull request, @ person, / prompt

StrideAI can make mistakes. Changes to Azure DevOps always need your approval.

This is the first screen your team sees. Pick a role above to change the quick starts, or {{ hubMoreLabelLower }} →

{{ f.t }}

{{ f.d }}
Watch it work

A story becomes four tasks, with your approval

One click on a work item, one approval card, and Undo if you change your mind. Rebuilt from the extension with sample data.

dev.azure.com/contoso/Shop/_workitems/edit/1234Simulated
contoso / Shop / Boards / Work itemsSprint 14 · Web Team
User Story 1234
Pay with a saved card
Emily Carter
Active
Details
StrideAI
History
Links
Description

As a returning customer I want to pay with a card I saved earlier, so that I don't type the card number at every checkout.

Acceptance criteria
  1. A customer can save a card at checkout.
  2. A customer can pay with a saved card.
  3. A customer can delete a saved card.
  4. Only tokens are stored, never card numbers.
Discussion
EC
Emily Carter · 2 days ago
Spike #1240 is done: we go with the provider's token vault, no card data in our database.
RM
Raj Mehta · yesterday
Can we break this down before planning on Thursday? Nothing is estimated yet.
ME
Add a comment. Use # to link a work item, ! for a pull request.
Development
feature/1234-saved-cards· 3 commits · updated yesterday
!812 Card vault: token storage and provider clientDraft
{{ childHead }}
1240Spike: PCI rules for stored cardsClosed
{{ k.id }}{{ k.t }}{{ k.h }}
Planning
Story Points
8
Priority
2
Iteration
Shop\Sprint 14
Area
Shop\Web
Tags
checkoutpaymentspci
StudioOne click, one result. Changes still wait for your approval.
{{ t.t }}
{{ t.d }}
Message StrideAI · # work item, ! pull request, @ person, / prompt
Break this story down into tasks
✓ Read #1234 ✓ Read 1 child item Planning the remaining work…

The story has 4 acceptance criteria. The PCI spike #1240 is done, so I planned the remaining work as 4 tasks, 23 hours, each covering one criterion. They inherit the Web area and Sprint 14 from #1234.

Create 4 work itemsStrideAI needs your approval to change Azure DevOps
Task{{ k.t }}{{ k.h }}
DeclineCreate 4 items
✓ Created 4 work items under #1234Undo

{{ curNum }} · {{ curKind }} {{ curCap }}

    2.
Where it lives

Already where the work is

No new tool to open. StrideAI adds itself to the Azure DevOps pages your team uses every day.

{{ e.n }}
{{ e.t }}

{{ e.d }}
Rebuilt from the extension's cards, with sample data

Answers arrive as cards you can act on

{{ cardDesc }}

Backlog health: Testable
Sprint 24
Average
59 %
+8 since Oct 26
Items
5
A: 2
Need work
3
D: 2
Criteria by average score
{{ c.t }}{{ c.v }}
Per item · weakest first
{{ i.g }}#{{ i.id }} {{ i.t }}{{ i.weak }}{{ i.p }} %
Improve the weakest itemsSave findings as comments
Draft: 7 work itemsfrom Portal kick-off notes.docx
{{ intakeCount }} of 7 selectedFit 66 %
✓ Create {{ intakeCount }} itemsAsk for a different split
Edit here or tell StrideAI what to change. Creating still asks for your approval.
Medium risk6 files: 3 added, 3 changed, 0 deleted · test files: 1 · src/payments, src/checkout, db/migrations
Review of !482 · Add saved card payments

I read the 9 changed files and checked them against the acceptance criteria of #1234. The structure is clean, but two issues must be fixed before merging.

Blocking
  • src/payments/cardVault.ts:42: the full card token is written to the log (logger.info(token)). Log only the last four digits.
  • src/payments/savedCards.ts:88: deleting a card does not check that it belongs to the signed-in customer.
Should fix
  • src/checkout/PaymentStep.tsx:131: no message is shown when a saved card is declined.
Suggestion
  • Add a test for an expired saved card (acceptance criterion 3).
Vote on pull request !482
StrideAI needs your approval to change Azure DevOps
VoteWait for authorCommentTwo blocking issues: the card token is logged in cardVault.ts:42, and deleting a card does not check its owner (savedCards.ts:88). Details are in the comments.
DeclineSubmit vote
Agent management

AI teammates your team defines and manages

Give StrideAI a role written by your own team: a Product Owner, a QA Lead, an Architect. Each teammate has its own instructions, tool limits, and duties it runs on its own. Every change still waits for your approval.

See how teammates work
You stay in control

Every change takes the same five steps

StrideAI can't delete work items, pages, branches, or pipelines, and it sees only what the signed-in person can see.

{{ g.n }}
{{ g.t }}

{{ g.d }}
Secrets are replaced with a placeholder such as [hidden: JSON Web Token] before anything is sent to a model. How it works →
Get started

Set up once for the whole project

Free. Works on Azure DevOps Services and Azure DevOps Server 2020, 2022, and later.

Install from Marketplace

The Marketplace listing is private for now. This button links to it once the public URL is set.
  1. 1Install the extension in your organization or collection.
  2. 2A Project Administrator or StrideAI manager opens Project settings > StrideAI Assistant and adds a connection: the provider, one or more models that support tool calling, and an API key for the project or one per person.
  3. 3Click Test models, then Save.
  4. 4Open StrideAI Assistant > Chat in the project menu, or the StrideAI tab on any work item or pull request, and start asking.
Planned · MIT

Open source with 1.0

The community edition is planned under the MIT license, with every feature included. The public repository opens with the 1.0 release.

Optional

StrideAI Models

Teams without an Azure OpenAI, OpenAI, or Claude account can add a StrideAI Models connection with an access key. Nothing is gated; all features stay free.

Private

Need to talk in private?

Azure DevOps Server rollouts, security questionnaires, a model on your own network, or a question you would rather not post on GitHub. Write to us directly.

Contact us →

Questions

{{ f.q }}

{{ f.a }}
Features · v0.54

Everything it can do, by area

Every area can be turned off per project in Settings > Features. Changes always wait for approval.

{{ f.n }} · {{ f.tag }}

{{ f.t }}

{{ f.ask }}

{{ f.d }}

In your pipelines

Five tasks run on your agents with the pipeline's own identity. The model is optional for every task; keys are passed as secret variables.

# Pull request validation
- task: StrideAIReview@0
  inputs:
    provider: azure
    endpoint: https://contoso.openai.azure.com
    model: gpt-4.1
    apiKey: $(StrideAIKey)   # a secret variable
    failOn: secrets

# After a release build
- task: StrideAIReleaseNotes@0
  inputs:
    wikiPath: Release notes/$(Build.BuildNumber)

# Every morning
- task: StrideAIWatch@0
  inputs:
    windowHours: 24

# On a schedule
- task: StrideAIChecks@0
  inputs:
    team: Web Team
    failOn: critical
Roadmap

What's coming next

Planned work, in order. Plans can change, and nothing here is in the product yet.

{{ r.when }}
{{ r.t }}
  • {{ i.t }}
Follow on GitHub →
How it works

Your browser, two destinations

The browser talks only to your Azure DevOps organization or server, and to the model endpoints your Project Administrator or StrideAI manager approved.

Your tenant
Azure DevOps

Serves the extension's static files. REST calls use the signed-in person's permissions. Settings, usage, and the activity log are stored here.

Runs here
Your browser

Chat, model routing, skills, tools, redaction, guardrails, cards. Conversations, notes, and cached project data stay in the browser's own database.

Your account
Model endpoint

Azure OpenAI, Microsoft Foundry, OpenAI, Anthropic, or an OpenAI-compatible API, over HTTPS, under your own agreement with that provider.

No StrideAI server, database, or account. No telemetry. No third-party scripts, fonts, or images.

What happens when you ask

{{ g.n }}
{{ g.t }}

{{ g.d }}

Where data is stored

{{ s.t }}

{{ s.d }}

Permissions

Work items · read, writeCode · read, writeProject and team · read, writeBuild · read, executeRelease · read, write, execute, manageTest management · read, writeWiki · read, write

StrideAI doesn't ask for the Advanced Security permission. The pipeline tasks don't use these permissions: they run with the pipeline's own identity.
Generate

From a story to tests and code you can commit

Ask "Generate Playwright tests for #4312" or "scaffold the exporter module". StrideAI reads how your repository does it, then writes complete files with their paths, what they cover, and what they don't cover yet.

tests/e2e/export-orders.spec.tsTypeScript · PlaywrightSample data
import { test, expect } from "@playwright/test";
import { signIn } from "../support/session";

test.describe("Export orders as CSV (#4312)", () => {
  test("downloads the filtered orders", async ({ page }) => {
    await signIn(page, "finance");
    await page.goto("/orders?status=paid");
    const download = page.waitForEvent("download");
    await page.getByRole("button", { name: "Export CSV" }).click();
    expect((await download).suggestedFilename()).toMatch(/orders-.*\.csv/);
  });
});
Covers
  • Export of the filtered list
  • File name and format
Not covered yet
  • Exports above 10,000 rows
  • A user without the finance role
Commit in a pull requestDownload this file
Generated code needs a human review; the commit still asks for your approval.

The same work, with the typing removed

Without StrideAI
  • {{ b.t }}
With StrideAI
  • {{ b.t }}
What it generates

One story, six kinds of output

{{ e.t }}

{{ e.d }}

Generated files are a draft. Review them before merging; committing them always goes through a new branch, a pull request, and your approval.
For teams

Built for the whole team

Pick a role to see what people in it ask most. In the product, the same seven roles set the quick starts in every new chat.

{{ q.ask }}

{{ q.get }}

{{ q.kind }}

For teams with strict rules

StrideAI does not claim any industry certification. What it offers is an architecture you can check yourself.

{{ e.t }}

{{ e.d }}
Time saved estimator

Estimate the hours your team gets back

This uses the same model as Insights in the product: every change you approve counts for a set number of minutes. The minutes below are the product's defaults; the weekly counts are example values. Change both to match your team.

Average pay per person
{{ rateNote }}
Approved changes per person, per week
{{ k.label }}{{ k.min }} min each {{ k.v }}
Hours saved per week
{{ hoursWeek }}
Hours saved per year
{{ hoursYear }}
Value of that time per year
{{ valueYear }}

An estimate, not a measurement. A year is counted as 46 working weeks. Monthly pay is counted as 160 hours and yearly pay as 1,840 hours. The amount does not include what your model provider charges. After you install, Insights shows the real numbers for your project.

Install from Marketplace
Agent management

A team of AI teammates, managed like the rest of your project

Define each agent in a short Markdown file, give it the tools it may use and the jobs it does on its own, and see all of them on one page. StrideAI's own rules always stay in place.

# .strideai/agents/product-owner/agent.md
---
name: Product Owner
description: Keeps the backlog ordered and ready
tools: read-only
skills: [backlog, sprints, story-splitting]
on: [bugInflow]
duties:
  - every day | sprint current | Draft the missing acceptance criteria
---

You help the product owner keep a backlog the team can act on.

- Start from the outcome. Ask what changes for the user.
- Prefer small, independent stories.

Define, assign, run, review

{{ g.n }}
{{ g.t }}

{{ g.d }}
{{ f.tag }}

{{ f.t }}

{{ f.d }}
Agents stay inside your rules

A teammate can narrow what StrideAI may do, never widen it

{{ e.t }}

{{ e.d }}
The StrideAI family

StrideAI Assistant is the first extension

StrideAI is a home for Azure DevOps extensions. The Assistant is the one available today; more extensions may follow under the same name and the same rules: in your browser, with your models, with your approval.

See the roadmap →
Industries

How StrideAI helps in your industry

The product is the same everywhere. What changes is which parts matter most. Pick an industry to see them.

{{ indName }}

{{ indNeed }}

{{ e.n }}
{{ e.t }}

{{ e.d }}

StrideAI does not hold or claim any industry certification. It runs inside your Azure DevOps with the model you choose, so your existing controls and agreements keep applying.
Roadmap

What we will build next

Planned work, in order. Each phase ships as its own version. Plans can change, and nothing marked as planned is in the product yet.

{{ r.when }}

{{ r.t }}

{{ r.d }}

{{ i.t }}

Recently shipped

{{ r.v }}{{ r.t }}. {{ r.d }}
Pricing

Every feature is free

There are no paid tiers and no feature gates. You bring a model you already have, or add StrideAI Models if you have none.

StrideAI Assistant
Free

The extension, with your own model.

  • {{ b.t }}
    •
Install from Marketplace
StrideAI ModelsOptional
Price to be announced

Hosted model access for teams without a model account.

  • {{ b.t }}
    •
Ask about early access

What you do pay for

The model. It runs in your own Azure subscription or provider account, at your provider's prices. StrideAI helps you keep that cost down and visible.

{{ e.t }}

{{ e.d }}
Estimate the time your team gets back →
Privacy and data

Your data stays in your hands

StrideAI talks only to your Azure DevOps and to the models your administrator approved. No StrideAI servers, no telemetry.

{{ e.t }}

{{ e.d }}

Where everything is stored

WhatWhere it is storedWho can see it
{{ s.a }}{{ s.b }}{{ s.c }}

You can delete chats from the chat history, and clear notes and cached data any time in Settings > Memory.

What is sent to the model

  • Your question and the conversation so far, and the screenshots you attach to your latest message.
  • The Azure DevOps data StrideAI reads to answer it, such as work item fields, code files, wiki pages, or pipeline logs.
  • Your name, the project name, a short summary of the project's process, teams, and repositories, the team's instructions, and saved notes.
Only when you send a message

It goes only to the approved model endpoints, and your provider's data terms apply. Secrets are replaced with a placeholder first.

Running a security review?

Send us your questionnaire or ask about a private deployment. We answer from [email protected].

Contact us
Changelog

Release notes

The latest versions, newest first. The full notes are in CHANGELOG.md in the repository.

{{ r.v }}
{{ r.t }}

{{ r.d }}
Contact

Talk to us in private

For anything you would rather not post publicly: a rollout on Azure DevOps Server, a security questionnaire, a model inside your own network, or early access to StrideAI Models. Bugs and feature ideas are welcome on GitHub.

{{ cErrorText }}

{{ cSentText }}
{{ cHint }}